---
title: 'Groundcover inCloud'
description: 'Configuring the Groundcover inCloud backend (Managed)'
sidebarTitle: 'Groundcover inCloud'
icon: 'signal-stream'
---

### Getting Started

<img src="https://d15jtxgb40qetw.cloudfront.net/groundcover.svg" alt="groundcover" className="not-prose h-20" />

{/*
    Add custom content here (under this comment)...

    e.g.

    **Creating Account**<br />
    Go to the **[🔗 website](https://odigos.io) > Account** and click **Sign Up**

    **Obtaining Access Token**<br />
    Go to **⚙️ > Access Tokens** and click **Create New**

    !! Do not remove this comment, this acts as a key indicator in `docs/sync-dest-doc.py` !!
    !! START CUSTOM EDIT !!
*/}

To get an API Key, refer to [these docs](https://docs.groundcover.com/architecture/incloud-managed/ingestion-endpoints#fetching-the-api-key).

{/*
    !! Do not remove this comment, this acts as a key indicator in `docs/sync-dest-doc.py` !!
    !! END CUSTOM EDIT !!
*/}

### Configuring Destination Fields

<Accordion title="Supported Signals:">
  ✅ Traces
  ✅ Metrics
  ✅ Logs
</Accordion>

- **GROUNDCOVER_ENDPOINT** `string` : Groundcover inCloud Site. The format is `host:port`. Host is required, also known as your `inCloud_Site`, it is part of the configuration provided to you by Groundcover when setting up inCloud Managed. Port is optional, and defaults to the default OpenTelemetry gRPC port `4317`.
  - This field is required
- **GROUNDCOVER_API_KEY** `string` : Groundcover API Key.
  - This field is required

### Adding Destination to Odigos

There are two primary methods for configuring destinations in Odigos:

##### **Using the UI**

<Steps>
  <Step>
    Use the [Odigos CLI](https://docs.odigos.io/cli/odigos_ui) to access the UI
    ```bash
    odigos ui
    ```
  </Step>
  <Step>
    Click on `Add Destination`, select `Groundcover inCloud` and follow the on-screen instructions
  </Step>
</Steps>

##### **Using Kubernetes manifests**

<Steps>
  <Step>
    Save the YAML below to a file (e.g. `groundcover.yaml`)
    ```yaml
    apiVersion: odigos.io/v1alpha1
    kind: Destination
    metadata:
      name: groundcover-example
      namespace: odigos-system
    spec:
      data:
        GROUNDCOVER_ENDPOINT: <Groundcover inCloud Site>
      destinationName: groundcover
      secretRef:
        name: groundcover-secret
      signals:
      - TRACES
      - METRICS
      - LOGS
      type: groundcover

    ---

    apiVersion: v1
    data:
      GROUNDCOVER_API_KEY: <Base64 Groundcover API Key>
    kind: Secret
    metadata:
      name: groundcover-secret
      namespace: odigos-system
    type: Opaque
    ```
  </Step>
  <Step>
    Apply the YAML using `kubectl`
    ```bash
    kubectl apply -f groundcover.yaml
    ```
  </Step>
</Steps>